Currently, the language service defaults notebooks to the workspace configuration target profile, which can cause incorrect errors when the workspace is set to a restrictive profile like "base". This creates a mismatch with the Python runtime behavior where notebooks should use unrestricted operations by default.

• Identify the issue with notebook target profile defaulting to workspace settings
• Move default logic to VS Code layer instead of Rust layer (based on code review feedback)
• Implement solution in getQSharpConfigMetadata() to return { targetProfile: "unrestricted" } by default
• Add VS Code integration test to verify notebooks default to unrestricted profile
• Verify all existing tests continue to pass
• Update PR description to reflect final implementation approach

Problem

When a user sets their workspace target profile to "base" and opens a Jupyter notebook with Q# code that uses unrestricted operations (like measurement results in conditionals), the language service incorrectly shows errors:

%%qsharp

operation Foo() : Unit {
    use q = Qubit();
    H(q);
    if (M(q) == One) {  // Error: "cannot use a dynamic bool value"
        Reset(q);
    } else {
        X(q);
    }
}

Solution

Modified the VS Code notebook configuration logic to default to "unrestricted" target profile when no explicit configuration is provided via qsharp.init(), rather than falling back to the workspace configuration.

Changes

• Updated getQSharpConfigMetadata() in vscode/src/language-service/notebook.ts to return { targetProfile: "unrestricted" } when no Q# config metadata is found
• Added VS Code integration test notebook.test.ts to verify notebooks default to unrestricted profile behavior
• Created test notebook test-unrestricted-default.ipynb that contains unrestricted operations without explicit configuration

Testing

• Added integration test "Notebook defaults to unrestricted target profile" to verify the fix
• Test ensures no target profile related diagnostics appear for unrestricted operations in notebooks without explicit configuration
• All existing tests continue to pass

This ensures notebooks behave consistently with Python runtime behavior while still allowing explicit target profile configuration when needed via qsharp.init().

Fixes #2525.